feat: pre-messages / next version of download on demand#7371
Merged
Conversation
6fe6723 to
8140ebc
Compare
2f1c383 to
6bcc795
Compare
26 tasks
8443b17 to
702771f
Compare
Hocuri
reviewed
Dec 11, 2025
bb0fd7c to
a98fe05
Compare
Hocuri
reviewed
Dec 18, 2025
iequidoo
reviewed
Dec 22, 2025
iequidoo
reviewed
Dec 24, 2025
iequidoo
reviewed
Dec 27, 2025
iequidoo
reviewed
Dec 28, 2025
This comment was marked as resolved.
This comment was marked as resolved.
4a119fc to
84ce946
Compare
This comment was marked as resolved.
This comment was marked as resolved.
iequidoo
reviewed
Dec 30, 2025
This comment was marked as resolved.
This comment was marked as resolved.
18346a1 to
77ab447
Compare
It currently fails because pre-messages aren't deleted on IMAP.
Hyphen shouldn't be surrounded by spaces in general.
…th pre-message ones When inserting pre-message checks in the middle, if they evaluate to false, the remaining checks aren't performed. While this may be correct currently, it's hard to maintain. Better move the pre-message checks into a separate block.
…_pre_message() Now it goes before `scan_folders()`. Scanning folders isn't that important, it's even debounced to once per minute. Before, `download_msgs()` even preceded the whole `fetch_idle()`.
…s as seen on IMAP
It's the post-message metadata by its nature and it's even put into the Chat-Post-Message-Metadata header.
This shouldn't cause message reordering issues because the UIs don't allow to set too small DownloadLimit, but this will help download small, e.g. chat messages first and only then big emails. Even if we decide to revert this suggestion, the test is still useful.
It never worked as expected: if messages showed up on IMAP later, they weren't deleted. Messages must be trashed with the `deleted` flag set, not just deleted from the db.
I.e. if DeleteServerAfter is set or BccSelf is unset (single-device mode) for chatmail. Looks like this never worked as expected.
This comment was marked as outdated.
This comment was marked as outdated.
link2xt
approved these changes
Jan 8, 2026
Collaborator
link2xt
left a comment
There was a problem hiding this comment.
I will merge this as one commit after tagging 2.37.0. Any additional changes can be separate PRs on top.
Collaborator
|
There's no good commit message however. I think in such cases we need to copy the description from the issue, it's good enough here ("Motivation" and "Implementation" sections look enough). Otherwise w/o access to github it will be hard to understand many things. I'd consider amending the commit and force-pushing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DC_STR_DOWNLOAD_AVAILABILITY#7369This is the branch for #7367
closes #7367
Currently removed tests
Progress of the tests
Overview about the recycled(♻️) and dropped(🗑️) tests of the tests that I removed in #7373
All the recycled tests were already recycled/re-made except for some which are still to do:
(none)
Furthermore there need to be new tests to test the downloading/scheduling changes.
TODO Tests
postponed to do tests
(none)
discarded/ignored test ideas
maybe we should reconsider / discuss those?
Known bugs: